Predicting future performance of multiple workers on crowdsourcing tasks and selecting repeated crowdsourcing workers

ABSTRACT

Systems and methods of a job distribution platform for aggregating performance data in a worker profile for workers in performing crowd sourced tasks are disclosed. In one aspect, embodiments of the present disclosure include a method, which may be implemented on a system, of generating and storing performance data when a worker performs one or more tasks distributed online to their respective computing devices by a job distribution platform which crowd sources tasks over a network to remote workers. The tasks can span current jobs and a history of previous jobs distributed to the worker and the job performance data for the worker is collected for current and previous jobs. New jobs can be assigned to a worker selected based on performance data of the worker. Other types of worker information may also be tracked and generated for multiple workers in various worker pools (channels), for example, psych questions or other more subjective data collected from a worker or contributor in addition to performance.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a divisional application of pending U.S. application Ser. No. 14/148,554 filed Jan. 6, 2014, which is a continuation application of, and incorporates by reference in its entirety, U.S. application Ser. No. 13/275,284 filed Oct. 17, 2011, now U.S. Pat. No. 8,626,545, issued on Jan. 7, 2014 and entitled “PREDICTING FUTURE PERFORMANCE OF MULTIPLE WORKERS ON CROWDSOURCING TASKS AND SELECTING REPEATED CROWDSOURCING WORKERS.”

This application is related to, and incorporates by reference in their entirety, U.S. application Ser. No. 12/817,946 filed Jun. 17, 2010 and entitled “DISTRIBUTING A TASK TO MULTIPLE WORKERS OVER A NETWORK FOR COMPLETION WHILE PROVIDING QUALITY CONTROL,” and U.S. application Ser. No. 12/817,979 filed Jun. 17, 2010 and entitled “USING VIRTUAL CURRENCY TO COMPENSATE WORKERS IN A CROWDSOURCED TASK.”

This application is related to, and incorporates by reference in its entirety, U.S. application Ser. No. 13/275,290 (Attorney Docket No. 73442-8005.US02) filed Oct. 17, 2011 and entitled “EVALUATING A WORKER IN PERFORMING CROWD SOURCED TASKS AND PROVIDING IN-TASK TRAINING THROUGH PROGRAMMATICALLY GENERATED TEST TASKS.”

TECHNICAL FIELD

The disclosed technology relates generally to outsourcing or crowd sourcing jobs and tasks while providing sophisticated worker performance tracking for quality enhancement and cost effectiveness.

BACKGROUND

Outsourcing mundane tasks and jobs to online labor around the globe has demonstrated potential in assisting entities and individuals complete a large amount of tasks in a time efficient manner. However, given the variability in labor pool, education level, age group, the results of the completed tasks are frequently less than ideal. Although entities could utilize crowd sourcing to have tasks completed in a short amount of time for a reasonable cost, the quality is typically highly variable and frequently unreliable.

Crowd sourcing is a growing industry, and online platforms exist for completion of tasks and microtasks. Labor-on-demand platforms provide APIs for application development and an international payment infrastructure for the deployment and implementation of crowd sourced tasks. Crowd sourcing has become a global phenomenon with a low barrier to entry. Millions of people around the world now participate in a digital and virtual workplace. However, the breadth and diversity among crowd sourcing participants, workers and researchers is immense and poses a challenge to implement adequate quality control mechanisms to account for a wide range of worker behavior: scammers, lazy workers, ethical workers, unethical workers, slow learners, etc. in a resource effective manner.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example block diagram of a host server of a job distribution platform that performs crowd sourcing by distributing tasks over a network to multiple workers and aggregates job performance data to generate worker profile data in performing crowd sourced tasks.

FIG. 2A depicts an example block diagram of the components of a host server of a job distribution platform that distributes (e.g., crowd sources) tasks or microtasks to workers online and providing enhanced quality control through use and aggregation of worker profile data.

FIG. 2B depicts an example block diagram of the components of a worker manager/tracker module of the host server able to generate and store performance data when a worker performs tasks distributed to them by a job distribution platform which crowd sources tasks over a network to remote workers.

FIG. 3 illustrates an example repository for storing worker/contributor performance and profile data.

FIG. 4 depicts a flow chart illustrating an example process for generating profile data for a worker or contributor in performing crowd sourced tasks.

FIG. 5 depicts a flow chart illustrating example processes for generating quantitative metrics to characterize job performance in performing crowd sourced tasks.

FIG. 6 depicts a flow chart illustrating an example process for using performance data to select a suitable worker to whom to distribute a crowd sourced task.

FIG. 7 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.

Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.

The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.

Without intent to further limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.

Embodiments of the present disclosure include systems and methods for providing crowd sourcing services with quality control mechanisms.

FIG. 1 illustrates an example block diagram of a host server 100 of a job distribution platform that performs crowd sourcing by distributing tasks over a network 106 to multiple workers 122 and aggregates job performance data to generate worker profile data in performing crowd sourced tasks.

The client devices 102A-N can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection with another device, a server and/or other systems. Client devices 102A-N each typically include a display and/or other output functionalities to present information and data exchanged between among the devices 102A-N and the host server 100.

For example, the client devices 102 can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, a handheld tablet (e.g. an iPad, a Galaxy, Xoom Tablet, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console, an iPhone, and/or any other portable, mobile, hand held devices, etc. The input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.

The client devices 102A-N, worker channels 108, workers (or contributors) 122, gaming server 110, third party social network server 112, payment processing server 114, and/or mobile credit payment server 116, can be coupled to a network 106. In some embodiments, the devices 102A-N and host server 100 may be directly connected to one another.

In one embodiment, the host server 100 is operable to perform crowd sourcing services and/or to process crowd sourcing requests for entities (e.g., companies, organizations or other types of institutions) or users (e.g., individual or groups of users). The host server 100 can distribute a task to be crowd sourced to multiple workers (who may be located through various different channels 108A-N) and provide sophisticated quality control and cost management mechanisms, including tracking worker data over a period of time to provide an indication of worker preference, level of expertise, responsiveness, value of work, performance, speed, and other like performance/quality metrics for the worker or the generated work product.

The host server 100 of the job distribution platform utilizes workers from multiple worker pools via different channels 108. The host server 100 can have a partnering relationship with one or more of the channels 108 Channels can be chosen by demographic requirements such as location and general age/sex of the worker pool. When a contributor completes the work required, the job distribution platform can inform the partner (or channel) that a transaction has completed for a specified amount. The partner can then award the contributor some percentage of the amount in either virtual or real currency. The access to multiple worker pools allows the job distribution platform access to a larger group of workers/contributors and enhances scalability and diversifies worker base. The worker pool which is used for a given job or task can be selected manually by the person posting the task and/or determined in part or in whole by the host server 100. Some pools have limitations, for example, some do not allow adult content, others do not provide the cultural or language needs of the task.

Quality control and the amount of quality desired can be configured by the requesting entity or user such that for example, a user or entity is only charged for the task if completed to the desired or target accuracy level. The channels 110 through which labor can be identified can include by way of example, but not limitation, Amazon Mechanical Turk, Give Work, SamaSource, Trial Pay (e.g., a virtual currency provider), third party social networks (e.g., Facebook, Twitter, LinkedIn, MySpace, third-party social network server 112) or gaming platforms (e.g., Gambit, Prodege, etc.) New and additional labor forces are constantly being integrated into the system and partnering with the host 100, each with their own advantages and disadvantages.

The host server 100, can in addition, also utilize social networks or social network servers (e.g., the 3rd party social network server 112) to aggregate, parse, and/or identify information such as preferences, likes/dislikes, language proficiency, general proficiency, interests, hobbies, expertise related information about workers or contributors which can be used in a worker profile and used as factors in selecting suitable workers for a given job or task.

In some instances, the host server 100 utilizes an online gaming service or platform (e.g., through a third-party gaming server 110 or other partnering platform) through which to distribute tasks or unit jobs and tasks. Gaming services which provide games to various types of online or web-based platforms can also be partnered with the host server 100 of the job distribution platform. Note that the host server 100 may also host gaming services via one or more gaming platforms. The unit jobs can be distributed to gamers or other visitors on the gaming platform. In one embodiment, the workers utilized in an online game can be paid in virtual currency, such as virtual currency that can be used to play games on the gaming server 110.

In some instances, the host server 100 utilizes a payment processing server 114 to facilitate payment of workers or contributors 122 in money. The payment processing server 114 can be integrated or operated by the same entity as the host server 100 of the job distribution platform, or it may be operated by a third party. The host server 100 manages the payment preferences of a given worker and ensure, for example, through the payment processing server 114 that the worker gets paid in the desired currency (e.g., U.S. dollars, Euro, etc.), at the desired frequency, in a desired channel (e.g., online, PayPal, direct bank account deposit, physical check, money order), in a desired format (e.g., money, mobile credits, gaming credits, or other types of virtual currency, etc.). For example, the host server 100 can also interact with a mobile credit payment service or mobile credit payment server 116 to facilitate the payment of workers or contributors with mobile credits. The mobile credit payment server 116 may be operated by a wireless network operator or another third party entity. In some instances, the host server 100 internally has mobile credit payment services which operates in whole or in part the payment/compensation of workers in mobile credits.

Functions and techniques performed by the host server 100 and the components therein are described in detail with further references to the examples of FIG. 2A-B.

The client devices 102A-N are generally operated by entities/users requesting crowd sourcing services, for example via user interface 104A-N displayed on the display units. The client devices may also be. The client devices 102A-N may also be used (e.g., by programmers and developers) by workers to access job units or tasks for completion.

In one embodiment, client devices 102 communicate with the host server 100 and/or notification server 150 over network 106. In general, network 106, over which the client devices 102, the host server 100, and/or notification server 150 communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.

The network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 100 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).

In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MIMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.

The host server 100 may include internally or be externally coupled to a user repository 128 and/or a tasks repository 130. The repositories can store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server 100 and/or any other servers for operation. The repositories may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.

The repositories can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.

In some embodiments, the host server 100 is able to provide data to be stored in the user repository 128, the tasks repository 130 and/or can retrieve data stored in the repositories. The user repository 128 can store user (e.g., worker) information, statistics, speed, accuracy, topics of interest, topics of expertise, etc. The tasks repository 130 can include, tasks or unit jobs (e.g., in spreadsheets or other types of files) specified by entities or individuals requesting crowd sourcing services. The repository 130 can also include information about the requesting entities or individuals.

One embodiment further includes a performance and profile data repository 132 which can store enhanced worker (e.g., contributor) performance information and metrics, worker preference information, demographic profile information, social network information, peer review information, etc. Additional details of examples of types of data stored in the repository 132 as illustrated with further reference to the example of FIG. 3.

FIG. 2A depicts an example block diagram of the components of a host server 200 of a job distribution platform that distributes (e.g., crowd sources) tasks or microtasks to workers online and providing enhanced quality control through use and aggregation of worker profile data.

The host server 200 can include, for example, a network interface 201, an attribute module 202, a task configuration module 204 having a budget manager, a wage setting agent 206 having a virtual currency manager, an accuracy manager module 208, a quality control module 210 having a statistics tracking module, a worker channel selection module 212 having a task distributor module and/or a gaming server manager, and/or a worker manager and tracker 220. Additional or less components/modules/engines can be included in the host server 200 and each illustrated component.

The network interface 201 can be a networking module that enables the host server 200 to mediate data in a network with an entity that is external to the host server 200, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 201 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

As used herein, a “module,” a “manager,” an “agent,” a “tracker,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, tracker, agent, handler, or engine can be centralized or its functionality distributed. The module, manager, tracker, agent, handler, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor.

As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.

One embodiment of the host server 200 includes an attribute module 202. The attribute module 202 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to identify, detect, extract, an attribute of a task, which generally includes multiple units.

An attribute of a task can include, by way of example but not limitation, level of difficulty of the task, level of subjectivity, etc. Task attributes can be specified or measured by an amount of time that is needed to complete the task. In addition, the attribute can include determining target accuracy specified by the entity or user requesting the crowd sourcing services.

Task attributes can be determined during a calibration process when the requesting entity is setting up jobs or tasks to be distributed to on-demand labor for completion. Timing, wages, and target accuracy can be determined and computed for a unit job or task.

One embodiment of the host server 200 includes a task configuration module 204. The task configuration module 204 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to configure a task or unit jobs for quality control and based on a user's specified parameters.

For example, the task configuration module 204 allows the user to upload or edit tasks/unit jobs via a web interface. In addition, the task configuration module 204 calibrates a task by identifying its attributes or attributes of a single unit job. For example, the task configuration module 204 determines the amount of time needed a certain unit job or task requires. This information can be used to determine the wage to pay a worker when they have completed their jobs, for example, by the wage setting agent 206.

One embodiment of the host server 200 includes a wage setting agent 206. The wage setting agent 206 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to set a wage amount that is offered to a worker for completing a unit job of the task based on the attribute and the target accuracy.

In general, the wage setting agent 206 can set the wage based on one or more of the attributes, level of target accuracy, the requestor's budget, etc. In addition, the requesting entity/user can specify a desired level of wage to pay each worker. In one embodiment, the system sets the wage dynamically. For example, the initial calibration of the wage can be an estimate and the actual wage is calculated as the job progresses. The system can continue to track the amount of time/resources needed by workers to complete a job. This way, the system can compensate for jobs that are taking workers different amounts of time from what was originally estimated. For example, while most jobs end up around $x/hr, but jobs that are extremely time sensitive can be much higher (e.g., as much as 4-20 x/hr). There is also a direct correlation between quality of the work and payment amount. Using the wage amount, the agent 206 can also determine the total cost to the requesting entity to complete the task using the total number of job units in the task. The wage setting agent 206 is configured such that the requestor (entity or user) can tweak the total cost by adjusting, one or more of, the target level of accuracy and the desired/ideal level of wage for paying the workers.

One embodiment of the host server 200 includes an accuracy manager module 208. The accuracy manager module 208 be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to determine, set, identify, the target accuracy in completion of the task by the entity.

The target accuracy can be, for example, specified by the entity/user requesting that a task be distributed to multiple workers (e.g., including online labor, on-demand labor) for completion. The target accuracy can be specified during calibration. The user/entity and indicate whether more or less accuracy is desired. Generally more accurate results require additional results to be obtained per job unit, thus potentially increasing the total cost to complete the task. In some instances, the target accuracy may be set by default rather than user customized.

One embodiment of the host server 200 includes a quality control module 210. The quality control module 210 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to implement quality control mechanisms to ensure that the results of the completion of the task are of a quality expected by the requestor.

The quality control module 210 can compute the number of results (e.g., judgments) needed per job unit based on the target accuracy. To compute the number of results, in one embodiment, a minimum number of judgments is initially set. If the measure of agreement is below a predefined percentage once the minimum number of judgments has been collected, more judgments can be collected until the predefined agreement has been met. A maximum number of judgments can also be set, for example to ensure jobs run within budget.

In addition, the quality control module 210 can manage the standards for each task used for quality control. For example, the quality control module 210 enables the requesting entity/user to specify a select set of unit jobs that are presented to online labor units for the entity to evaluate quality of task completion. The questions can be added. In general, the types of tasks that are good for the quality control are those with a right or wrong answer.

For these questions, the correct answers or responses are typically specified. The user/entity can also monitor/track the efficacy of the selected questions. A user can see each selected question and whether workers have correctly answered these questions. The user can also see, access, and/or track how many workers have responded to a selected question. Using the statistics, the user can modify the selection accordingly.

Using these questions, the quality control module 210 can determine the quality of the work and the quality of a particular worker's work product. For example, the quality control module 210 may include a statistics tracking module which tracks, collects and/or aggregates statistics of the online labor units completing the select jobs. In most instances, workers are able to choose any job that has been assigned as long as they meet certain requirements (e.g., age and/or language, etc.). However, workers can also be prohibited from working on a single job, single type of job, or all jobs. For example, workers history, statistics, and performance, can be used to target jobs to workers based on what they have performed well on. Workers are typically allowed to attempt any job they have not been blocked from. If it is the first time they have seen the task they will only be asked known questions. If they have not answered a pre-defined number of questions correctly within a certain time period they are typically not allowed to perform the actual task.

One embodiment of the host server 200 includes a worker selection module 212. The worker selection module 212 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to select workers (e.g., online workers, on-demand labor, etc.) to whom to distribute unit jobs of a task.

The worker selection module 212 can select a channel based on the user/entity's selection (e.g., Mechanical Turk, Crowdflower, Gambit (e.g., a third party gaming platform), Give Work, SamaSource, Trial Pay (e.g., a virtual currency provider), Gambit, Internal, etc.). New and additional labor forces are constantly being integrated into the system, each with their own advantages and disadvantages. Based on the selected channel, the task distributor can then distribute jobs to various workers for completion of unit jobs in the task.

In one embodiment, the selected channel is an online gaming environment in which gamers or other users are presented with unit jobs while playing games or doing something else. These users can be paid in virtual currency, for example, that they can use in the online gaming environment. Such a process can be performed by the gaming service manager. The gaming server manager can manage games internal to the host server 200 or manage communications with an external gaming server (e.g., the gaming server 110 shown in the example of FIG. 1). The tasks can be presented on a site hosted by the server 200 of presented to workers on the third party site.

In one embodiment, the gaming server manager in the worker channel selection module 212 communicates with the wage setting agent 206 to determine the wage that a worker/gamer would be entitled to upon completion of a unit job or task. The gaming server manager can then determine the amount of virtual currency to which the wage converts. The gaming server manager then communicate the tasks to be presented via the gaming site to the third party gaming server.

One embodiment of the host server 200 includes a worker manager and tracker module 220. The worker channel selection module 212 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to detect, track, compute, generate, determine, and/or identify job performance data or job performance-related data for multiple workers/contributors via the job distribution platform. Other types of worker information may also be tracked and generated for multiple workers in various worker pools (channels), for example, psych questions or other more subjective data collected from a worker or contributor in addition to performance.

Worker information including job performance data, can be tracked over a period of time (e.g., historical performance data) for a worker. For example, performance data can be tracked for a given task, a given job (a job can include multiple tasks), a session (e.g., a worker can work on multiple jobs and tasks during a given work session), a day, a week, a month, a year, etc. Useful statistical data can be generated or computed by the manager and tracker module 220 for the job distribution platform to more effectively and efficiently control quality of work product, extract/determine meaningful information about each individual worker/contributor, and/or allow jobs/projects to be more effectively cost managed. By tracking, aggregating, and storing performance data for multiple users across several worker pools, the job distribution platform can have access to useful information for distributing work and managing quality and cost.

Detailed features and functionalities of the worker manager and tracker module 220 are described with reference to FIG. 2B.

The host server 200 represents any one or a portion of the functions described for the modules. The host server 200 can include additional or less modules. More or less functions can be included, in whole or in part, without deviating from the novel art of the disclosure. The repositories 128 and 130 were discussed in conjunction with the description of FIG. 1. The repository 132 is described with further reference to the example of FIG. 3.

FIG. 2B depicts an example block diagram of the components of a worker manager/tracker module 220 of the host server 200 of the example of FIG. 2A able to generate and store performance data for a worker.

The performance data can be determined or generated when a worker performs tasks distributed to them by a job distribution platform (e.g., hosted by the host server 200) which crowd sources tasks over a network to remote workers.

The module 220 can include, for example, a job history tracker module 225 having a session tracker 226, a job tracker 227, a worker tracker 228 having an ID tracker 229 and/or a channel tracker 230. The module 220 can further include a performance data generator 250 having a performance agent 235, a device identifier 245, a quality assessor 240, a speed tracker 255, a value assessor 260, and/or an experience level assessor 265. The performance agent 235 can further include a rejection/judgment tracker 236, a bans tracker 237, and/or a performance flagging agent 238. The quality assessor 240 can include a peer review metric module 241 and/or a gold standard metric module 242. The speed tracker 255 may further include a velocity violation detector 256. The value assessor 260 can include an FTE metric module 261 and/or a financial value metric module 262.

The worker manager/tracker module 220 can further include a worker sentiment determination engine 270, a worker preference engine 275, a static profile data aggregator 280 having a demographic information generator 281, a dynamic profile data aggregator 285, a worker profile generator 290, and/or a worker selection engine 295. The worker preference engine 275 can further include a payment preference handler 276, an objectionable content preference handler 277, and/or a work time preference handler 278. The dynamic profile data aggregator 285 can include an employment information manager 286 and/or a social network data compiler 287.

Additional or less components can be included in the host server 200 and each illustrated component.

As used herein, a “module,” a “manager,” an “agent,” a “tracker,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, tracker, agent, handler, or engine can be centralized or its functionality distributed. The module, manager, tracker, agent, handler, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor.

As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.

One embodiment of the worker manager/tracker 220 includes a job history tracker module 225. The job history tracker module 225 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to monitor, track, determine, record, tasks, microtasks, jobs, projects that workers or contributors have worked on through the job distribution platform hosted by server 200. Job attributes, owners, details and the knowledge/expertise involved in each job/task/project can be determined, tracked, recorded for each worker or contributor performing the job and stored (e.g., in repository 132) in association with any quality or performance data for the worker.

The job history tracker module can track and store the jobs performed by workers in a given session (e.g., by the session tracker 226). For example, a worker can perform several jobs in a given work session (e.g., from the time a worker logs in to access work distributed by the job distribution platform to when the user logs out or times out, or stops working for a certain amount of time). A work session can also have a default time period duration (e.g., one day, a certain number of hours, user gets logged out of the system, a few days, etc.) as specified by the worker, job distribution platform, or a given job.

In a given work session, a worker/contributor can work on several projects or jobs, with each project or job having several tasks. The session tracker 226 can track the projects, jobs, and/or tasks that the worker has worked on in a given session and generate or compute statistics (e.g., job performance metrics) for a given project, job, or task in a given session or across multiple sessions. The statuses of the various projects, jobs, and/or tasks performed in a session can also be determined and stored. For example, the session tracker 226 can track one or more tasks that span current j obs and a history of previous jobs distributed to the worker and job performance data for the worker is collected for current and previous jobs.

Similarly, the job history tracker module can track the tasks performed by workers in a given job or across multiple jobs (e.g., by the job tracker module 227). The job tracker 227 can identify, record, and store tasks assigned to and/or performed on, worked on by the workers/contributors. The job tracker module 227 can track a history of previous jobs having tasks a worker has worked on. The statuses of various jobs and/or tasks worked on by workers/contributors can be determined and/or recorded. The worker tracker 228 can track workers that have worked in the sessions, jobs, projects, and on tasks.

In one embodiment, the worker tracker 228 assigns a unique identifier (e.g., using the ID tracker 229) to each unique worker/contributor who has worked on tasks assigned via the job distribution platform. The unique identifier can be used to identify worker profile information and/or worker performance data. The unique identifier can be assigned to the worker to be associated with the worker across various jobs and tasks. The worker manager/tracker 220 can also track a worker based on the worker pool or channel though which the worker is connected to the job distribution platform, for example, by the channel tracker 230. In some instances, a given worker may be a part of multiple worker pools and the unique worker ID can be assigned to a given worker regardless of their multiple worker pool affiliations.

The performance data generator 250 of the worker manager/tracker module 220 can be any combination of software agents and/or hardware modules (e.g., including processors and/or memory units) able to monitor, track, determine, record, job performance data over a period of time for workers/contributors performing work through the job distribution platform that crowd sources tasks to multiple workers.

In general, the job performance data can be collected when the worker performs the tasks distributed online to their respective computing devices by the job distribution platform. In one embodiment, the job performance data includes quantitative metrics which can be determined or computed by the performance agent 235 for various performance and/or quality measures. For example, the rejection and judgment tracker 236 can detect and record results submitted by a worker/contributor that were rejected as faulty or accepted as a correct result (e.g., a judgment). Managing the distribution of tasks can be performed by a task requisition system, for example, using a custom implementation of the in-memory repository or database (e.g., Redis). The repository can be optimized for ensuring redundancy and performing the corresponding de-duplication. For instance, de-duplication can be implemented such that no contributor or worker sees the same task more than a specified number (e.g., once, twice, three times, etc.). If a contributor or worker is rejected, the tasks they had previously completed can be re-routed to other contributors or workers.

In one embodiment, the job performance data includes quantitative metrics indicating a rate or number of instances of bans from the system of flags from assigned jobs, for example, by the bans or flag tracker 237. In general, a ‘flagged’ worker prevents the workers or contributors from continuing to work on a specific task, or set of tasks. If a worker is banned, it is generally a one time event, and prevents a worker from doing future work through the platform.

A worker/contributor may be banned from performing work through the platform or flagged from performing specific jobs or tasks when the quality or speed of the work does not meet a threshold, which can be set by the job or the job distribution platform. For example, a worker/contributor may be temporarily or permanently suspended from a job if a number of results they provided are inaccurate, or if they submit a certain number of inaccurate results in a certain amount of time, or if the worker does not complete a task within a specified time frame (e.g., by the job poster or the job distribution platform).

In one embodiment, the job performance data includes quantitative metrics indicating a rate or number of instances of the worker has been flagged for performance review but not actually banned from a job or task, for example, by the performance flagging agent 238. Flagging can occur manually or programmatically after certain thresholds have been met. For example, flagging occurs after a peer review system has indicated a contributor is not performing accordingly or showing indicators of poor performance (e.g., spelling mistakes, irrelevant answers, or any other subjective requirements detectable by reviewers). A worker/contributor may be flagged when their performance (e.g., as indicated by one or more performance metrics of quality or speed) falls below a certain threshold, which may be set by a job requestor and/or in part or in whole determined by the job distribution platform. The rate or number of instances when the worker has been flagged for performance review can be used in assessing overall quality/performance of the worker.

In one embodiment, the performance data generator 250 tracks a rate or time with which the worker completes the one or more tasks, for example, via the speed tracker 255. The speed tracker 255 can also determine the speed, rate with which, or amount of time it takes a worker to complete a job, on average over a period of time, over a set of tasks, or over a set of jobs, for example. The rate or time with which the worker completes a task can be used as an indication in a worker profile of how efficient the worker is.

The speed tracker 255 can also track instances when the worker performs or completes a task exceeding a rate or speed, which may be an indication that a worker is not paying attention to performing the assigned tasks. As such, the job performance data can include quantitative metrics indicating a rate or number when the worker has performed or completed one or more tasks exceeding a rate or speed. In addition, the job performance data can include quantitative metrics indicating an average rate or speed with which the worker can satisfactorily complete a task, which can be used as an indicator for efficiency and/or accuracy of the worker. Each or any of the above metrics of job performance can be tracked for workers for a given job, a work session, or a number of tasks.

In one embodiment, the value assessor 260 determines the value, either quantitative or qualitative value, of work generated by workers/contributors. For example, the financial/monetary value of work generated by workers can be determined by module 262 and included as a quantitative metric of job performance data stored for a given worker/contributor. In one embodiment, the quality assessor 240 can determine the accuracy of work generated by the worker using test jobs (e.g., jobs or tasks with known responses/answers). Using test jobs/tasks with known responses/answers, the quality/accuracy of a worker's work product can directly be determined and used in computing a quantitative metric indicating the accuracy of a worker's work product. Quality assessment using test jobs/tasks can be performed by the gold standard metric module 242. In addition, the quality assessment can be performed by the peer review metric module 241, where a worker's work product can be evaluated using results generated by other workers (e.g., determine whether they match or not).

One embodiment of the performance data generator 250 includes an experience level assessor 265 which can determine an experience level of the worker based on duration or tenure with the job distribution platform. The job performance data for workers can thus include quantitative and/or qualitative metrics indicating the experience level of the worker. In addition, experience level can be determined with respect to specific types of jobs/tasks (e.g., business listing verification, content generation, adult-content detection, search result verification, etc.), or with respect to specific disciplines (e.g., art, computer science, math, language, etc.) and indicated in the job performance data of the user profile.

In one embodiment, satisfaction and/or frustration level with the job distribution platform is determined, for example, by the worker sentiment determination engine 270 to be included in the profile data. For instance, quantitative metrics indicating the satisfaction or frustration levels can be included in a worker's profile data.

In one embodiment, the profile data further includes, identification of devices used by the worker to perform tasks distributed by the job distribution platform or a preference of the worker to use one or more devices to work on tasks or specific types of tasks. The devices can be identified by the worker preference engine 275, or the device identifier 245. In general, the worker preference engine 275 can determine, identify, track, record, or store the preferences of the workers. Worker preferences can be explicitly specified by the worker, determined from the worker pool or specific channel through which the worker is accessed, and/or inferred from worker behavior by the job distribution platform. Worker preferences can include an indication of a preferred time of day to perform tasks (e.g., by the work time preference handler 278), indication of willingness to perform tasks involving objectionable content or adult content (e.g., by the objectionable content preference handler 277).

Worker preferences can further include compensation preferences, which can specify preferred wage, preferred currency, and preferred type of currency and/or specify preferred payment mechanism including one or more of, direct deposit, indirect deposit, or mobile credits. Compensation preferences may be determined, tracked, and/or managed by the payment preferences handler 276.

The user profile for workers can also include static profile data created or aggregated by the static profile aggregator 280. For example, demographic profile information (e.g., including, but not limited to, gender, age, ethnicity, religion, education, location, etc.) of workers can be determined, tracked, received, processed, recorded and managed by the demographic information generator 281.

The user profile can also include dynamic profile data which can be collected, aggregated, determined, detected, inferred, tracked, processed, received, stored and/or recorded by the dynamic profile data aggregator 285. For example, employment status information for workers can be determined and tracked by the employment information manager 286. Social profile data and/or professional profile data can also be aggregated for workers, for example from social network services including third party social networks and servers. Dynamical profile elements generated from historical work data can also be used. For example, the aggregator 285 can determine or track workers' historical speed, accuracy, or answer distribution and make this information queryable through the contributor profile. The aggregator 285 can also apply learning algorithms to good signals to predict future performance of a worker.

The worker profile generator 290 can use any combination of or all of the above user data including, but not limited to, quantitative and/or qualitative performance metrics for worker performance quality indicating accuracy, efficiency, knowledge, financial value, and/or expertise, worker preference (explicit or non-explicit), static or dynamic profile data (e.g., demographic information, real-life employment information, social network, presence, location information) to generate a worker profile for the worker.

The worker profile or any of the information contained therein can be used by the worker selection engine 295 in selecting a suitable worker from the repeat workers for a given task. For example, a given worker or workers can be selected to perform the new job based on worker preferences indicating willingness or unwillingness to work on objectionable or controversial content, or other criteria related to experience level, efficiency, or overall quality/accuracy.

FIG. 3 illustrates an example repository 332 for storing worker/contributor performance and profile data.

The performance and profile data can include information aggregated or determined by the worker manager/tracker 220 shown in the example of FIG. 2 and the various components therein. As described in FIG. 2, the worker profile elements can include static data 334, dynamic data 336, worker preference information 338, and/or performance data 340. An example listing of each category of worker profile data is shown. Metrics for performance data can be quantitative (as shown in the example of FIG. 3) or qualitative (e.g., good, bad, average, or assigned a letter grade (P/NP, A, C, D, etc.). Other types of metrics of measure can also be used.

FIG. 4 depicts a flow chart illustrating an example process for generating profile data for a worker or contributor in performing crowd sourced tasks.

In process 402, a worker/contributor performs one or more tasks distributed online to their respective computing devices by a job distribution platform. In process 404, a history of previous jobs having the one or more tasks the worker has worked on is tracked. Using the previous jobs and in addition, current jobs, performance metrics are determined in accordance with example steps at Flow A shown in the example of FIG. 5.

In process 406, the job performance data is aggregated over a period of time for the worker to generate the profile data. In addition, profile information for the worker can be aggregated in process 408. Preference information can be aggregated in process 410. In process, 412, profile data for a worker who performs crowd sourced tasks can be generated using any or all of the above worker information.

FIG. 5 depicts a chart illustrating example processes for generating quantitative metrics to characterize job performance in performing crowd sourced tasks. For example, in step 502 a rate or time with which the worker completes the one or more tasks can be tracked. In step 504, financial value of work generated by the worker can be determined. In process 506, accuracy of work generated by the worker can be determined using test jobs. In process 508, experience level of the worker can be determined. In process 510, accuracy of work generated by the worker using test jobs can be determined. In process 512, various quantitative metrics for the job performance data can be generated using any combination of or all of the above analysis. Qualitative metrics can also be generated and included in the worker profile using the above analysis.

FIG. 6 depicts a flow chart illustrating an example process for using performance data to select a suitable worker to whom to distribute a crowd sourced task.

In process 602, a test job is used to compare results generated by multiple workers. In process 604, accuracy of work generated by a worker based a comparison of the results to the test job. In process 606, performance data is generated when a worker performs one or more tasks distributed online to their respective computing devices (e.g., using the results of the test job). In process 608, the performance data is stored by the job distribution platform which crowd sources tasks over a network to remote workers. In process 610, a worker can be selected based on the performance data of the worker. In process 612, a new job can be assigned to the selected worker.

FIG. 7 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.

The network interface device enables the machine 2800 to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.

Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.

The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.

Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.

These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.

While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. § 112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. § 112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure. 

1-33. (canceled)
 34. A method performed by a job distribution server to track performance data and select a worker to perform a new crowdsourcing task, the method comprising: generating a first performance data based on a first worker completing a first crowdsourcing task and a second performance data based on a second worker completing a second crowdsourcing task, wherein each of the first performance data and the second performance data includes a monitored speed rate of the first or second crowdsourcing task and an average speed rate among a plurality of workers to satisfactorily complete any crowdsourcing task; aggregating all performance data associated with the first worker and all performance data associated with the second worker, wherein the aggregated performance data includes an average monitored speed rate differential indicating the difference between the monitored speed rate of each worker in completing the first and second crowdsourcing tasks and the average speed rate; suspending the first worker from completing the new crowdsourcing task based on determining that the average monitored speed rate differential of the first worker falls below a threshold speed rate; and re-routing the new crowdsourcing task from the first worker to the second worker.
 35. The method of claim 34, wherein said re-routing is based on determining that the average monitored speed rate differential of the second worker exceeds the threshold speed rate.
 36. The method of claim 34, wherein the first and second crowdsourcing tasks include a history of previously completed crowdsourcing tasks distributed to the first and second workers, where the first and second performance data for the first and second workers is collected for the first and second crowdsourcing tasks and the history of previously completed crowdsourcing tasks.
 37. The method of claim 36, further comprising: tracking the history of previously completed crowdsourcing tasks including the first and second crowdsourcing tasks.
 38. The method of claim 34, wherein the first and second performance data includes quantitative metrics indicating a rate or number of rejected results in performing the first and second crowdsourcing tasks.
 39. The method of claim 34, wherein the first and second performance data includes quantitative metrics indicating a rate or number of instances of bans from the first and second crowdsourcing tasks.
 40. The method of claim 34, wherein the first and second performance data includes quantitative metrics indicating a rate or number of instances that the first or second worker has been flagged for performance review.
 41. The method of claim 34, further comprising: tracking a rate in which the first or second worker completes the first or second crowdsourcing tasks.
 42. The method of claim 41, further comprising: tracking a number of instances that the first or second worker performs any of the first or second crowdsourcing tasks that exceed the average speed rate.
 43. The method of claim 34, wherein the first and second performance data includes quantitative metrics indicating a rate in which the first or second worker has completed one or more tasks exceeding the average speed rate.
 44. The method of claim 34, wherein the first and second performance data includes quantitative metrics indicating the monitored rate of speed in which the worker satisfactorily completes the first or second crowdsourcing task.
 45. The method of claim 34, further comprising: determining a value in completing any of the first or second crowdsourcing task by the first or second worker, wherein the first and second performance data includes quantitative metrics indicating the values of previous crowdsourcing tasks by the first or second worker.
 46. The method of claim 34, further comprising: determining an accuracy of work generated by the first and second workers using test jobs, wherein the first and second performance data includes quantitative metrics indicating the accuracy of the work performed by the first and second workers.
 47. The method of claim 34, further comprising: determining an experience level of the first and second workers based on time durations that the first and second workers have completed previous crowdsourcing tasks stored at the first and second performance data.
 48. The method of claim 34, wherein the first and second performance data further includes demographic data of the first and second workers.
 49. The method of claim 34, wherein first and second performance data further includes identification of devices used by the first and second workers to perform the first and second crowdsourcing tasks distributed by the job distribution server.
 50. The method of claim 34, wherein the first and second performance data further includes preferences of the first and second workers specified by the first and second workers, where the preferences of the first and second workers indicate a willingness to perform the first and second crowdsourcing tasks that involve objectionable content.
 51. The method of claim 34, wherein the first and second performance data further includes preferences of the first and second workers specified by the first and second workers, wherein the preferences of the first and second workers indicates a preferred time of day to perform the first and second crowdsourcing tasks.
 52. The method of claim 34, wherein the first and second performance data include compensation preferences which specify a preferred payment mechanism including-at least one of a direct deposit, indirect deposit, and mobile credit.
 53. The method of claim 52, wherein the compensation preferences further include at least one of a preferred wage, preferred currency, and preferred type of currency.
 54. The method of claim 34 wherein the first and second crowdsourcing tasks are distributed to the first and second workers via multiple channels, wherein the first and second workers perform the first and second crowdsourcing tasks through multiple channels, and where each of the first and second crowdsourcing tasks are tracked by a unique identifier.
 55. A system to track performance data and select a worker to perform a new crowdsourcing task, the system comprising a job distribution server configured to: generate performance data upon completion of an assigned crowdsourcing task for each of a plurality of workers that have completed at least two past crowdsourcing tasks, wherein the performance data includes a monitored speed rate of the worker in completing the assigned crowdsourcing task and an average speed rate of the worker to complete any crowdsourcing task and the past crowdsourcing tasks; aggregate all performance data associated with each worker of the plurality of workers, wherein the aggregated performance data includes an average monitored speed rate differential indicating a difference between the monitored speed rate of each worker and the average speed rate of the plurality of workers; suspend a first worker from completing a new crowdsourcing task based on determining that an average monitored speed rate differential associated the first worker falls below a threshold; and route the new crowdsourcing task from the first worker to a second worker that includes an average monitored speed rate differential that exceeds the threshold.
 56. The system of claim 55, further comprising: providing a test job to the first worker and second worker; obtaining a set of results from the first worker and second worker based on the test job; determining an accuracy of the results provided-by the first and second workers in performing the test job based on comparing the set of results provided-by the first and second workers; and updating performance data associated with the first worker and second worker based on the determined accuracy of the results provided-by the first and second workers in performing the test job, wherein said routing the new crowdsourcing task from the first worker to the second worker is based on the updated performance data associated with the first worker and second worker. 